7.2 Storing images on the web server

Note: By default, MyID will store new images in the database rather than on the web server. If you need to switch your system over to storing images on the web server, contact customer support, quoting reference SUP-218.

Switching your system to store captured images on the web server affects only images captured using the Image Capture window in MyID Desktop; it does not affect images captured for facial biometrics using Aware PreFace or images imported through the Lifecycle API.

Important: Do not switch your system to storing images on the web server if you are using the MyID Operator Client to capture images. The MyID Operator Client will experience errors if you attempt to capture images when your system is configured to store images on the web server.

If your system has any images on the web server (for example, if you have an upgraded system, where previously-captured images are on the web server while new images are stored in the database), you must configure the rest.core web service with the image location, or the MyID Operator Client will be unable to display the images; see the Displaying images stored on the web server section in the MyID Operator Client guide for details.

The following settings are applicable only if you are capturing images and storing them on the web server.

• Set Validate Image Size if you want image capture to validate the size and type of the image. This makes sure that the images uploaded conform to the Maximum Image Height and Maximum Image Width settings.

• If the web services server is not the same server as the web server, you must set the Image Upload Server configuration option. See the Setting the location of the web server section in the Web Service Architecture guide.

  You must have the following DLL registered on the image upload server:

  FileTransfer.dll

  You can find this DLL in the Components\Core folder in your MyID installation.

• The File Store Location is the physical location used to store uploaded images. This folder is mapped to the Upimages virtual directory in MyID.

  Note: The named MyID COM and MyID web service users must have write permission to this folder.

  By default, MyID uses the \Web\WebPIV\upimages folder on the web server.

  If you change this setting you must change the virtual directory in IIS. See section 7.2.3, Changing the upload images virtual directory for details.

• Maximum Number Of Sub-Folders specifies the maximum number of folders that will be created within the location specified in File Store Location. The default is 0.

• Preload Images allows an existing image to be associated with a cardholder. Set this to:

  • Yes to automatically associate an image in the image store with the cardholder. The filename of the image must match the cardholder’s logon name. For example, if the cardholder’s logon name is Jane Smith, the filename may be Jane Smith.jpg.
  • No (the default) ignores any existing images.
  • Ask – if an operator saves a record without capturing an image and MyID finds one with the appropriate filename, the operator is asked if the image is to be used.

7.2.1 Using sub-folders

If you have a large number of images in your uploaded images folder (by default, \Web\WebPIV\upimages) you may find that this decreases performance when uploading and retrieving images. To remedy this, you can set MyID to create a number of subfolders within the uploaded images folder; new uploaded images will be uploaded to one of the subfolders, ensuring that no single folder contains too many images.

To set the number of subfolders:

1. From the Configuration category, select Operation Settings.
2. Click the Video tab.

3. Set the Maximum Number Of Sub-Folders option to the number of folders you want to use.

   For example, type 50.

   The default is 0, and the maximum is 1000.

4. Click Save changes.

Once MyID has refreshed its configuration options (you may have to log out and log back in again) newly-uploaded images will be allocated to subfolders with names in the format z000 to z999.

MyID handles all the relative paths to the images automatically.

7.2.2 Port settings

Image upload uses the same protocol (HTTP or HTTPS) as you use to access the MyID website. If you have changed the default port used when you access MyID, you can set the HTTP or HTTPS port for uploading images:

• HTTP Port for image upload – default 80. Change this if you want to use image upload over HTTP with a different port number.
• HTTPS Port for image upload – default 443. Change this if you want to use image upload over HTTPS with a different port number.

7.2.3 Changing the upload images virtual directory

If you are storing images in the file system and not in the database, you can change the value of the File Store Location. To do this:

• Map the upimages virtual directory to the new location.
• Copy any existing images from the original to the new location.
• Set the correct IIS execute permissions.

Use the Internet Information Services Manager to map the upimages virtual directory to the new location.

1. From the Control Panel, select Administrator Tools, then Internet Information Services (IIS) Manager.

   Note: These instructions assume you are using IIS 10. If you are using a different version of IIS, see your Microsoft documentation for information on how to carry out these changes.

2. Expand Sites then Default Web Site.

3. Map the upimages virtual directory at this level to the File Store Location.

   1. Select the upimages virtual directory.
   2. In the Actions pane, click Basic Settings.
   3. Click the browse button next to the Physical path box and navigate to the File Store Location you specified in Operation Settings.
   4. Click OK.

4. Make the same change to the upimages virtual directory in each of the language folders.

   For example, make the same change to the following virtual directories:

   • Default Web Site > MyID > en > upimages

   • Default Web Site > MyID > us > upimages

5. Restart IIS.

   1. Select the Default Web Site.
   2. In the Manage Website pane, click Restart.
   3. Copy any existing images to the new location.

Important: You must ensure that IIS execute permission is disabled on the upimages folder. If it is not already configured, you must create a file called web.config in the upimages folder, containing the following text:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <handlers accessPolicy="Read" />
        <directoryBrowse enabled="false" />
        <httpErrors>
            <clear />
        </httpErrors>
    </system.webServer>
</configuration>